For reference: this fix is for an issue originally logged against fge/jackson-coreutils (issue 12)

we also need this exact fix too in order to pick up a newer version of guava

Hi @huggsboson, thanks for forking this project. Can you say anything about the likely timeline for this to be merged (and then I suppose a .jar would also need to be published for people to reference) ?

@huggsboson please help to cut another release with this PR?

I'll crank one out, but won't be able to do it until later in the day.

@huggsboson ping :-)

tested locally

merged

sorry it took so long @lukeu @dantran . I've got a 1.9 uploaded to mavencentral and i'll work on wiring it through json-patch and json-schema-core

patch is up to date with the new dependency at 1.10:

<dependency>
  <groupId>com.github.java-json-tools</groupId>
  <artifactId>json-patch</artifactId>
  <version>1.10</version>
</dependency>

now for schema-core and then validator.

json-schema-core should be updated with the new dependency.

<dependency>
  <groupId>com.github.java-json-tools</groupId>
  <artifactId>json-schema-core</artifactId>
  <version>1.2.9</version>
</dependency>

json-schema-validator should be updated with the new dependency (plus a few other changes):

<dependency>
  <groupId>com.github.java-json-tools</groupId>
  <artifactId>json-schema-validator</artifactId>
  <version>2.2.9</version>
</dependency>

k. All the libraries are updated. Let me know if you run into any problems. Also @lukeu I'd love to add you to the repositories / maven so you can help with merging and releasing if you're interested.

I am able to pickup json-schema-core 1.2.9 which has the fix for this PR.

Not able to upgrade to latest json-schema-validator, due to test failure at my app.

I now can use newer version of guava

Thanks to the new release

yes i am stuck with json-schema-validator-1.2.8. very likely the changes at 1.2.9 causing my app junit test to fail. We spend some time to look into details

here is error string extracted from build log ( not I am not the owner this test case)

Expected: a collection containing "/links/0: object has missing required properties (["href"])"
but: was "/createdTime: string "2015-05-23T10:44:04.295+0200" is invalid against requested date format(s) [yyyy-MM-dd'T'HH:mm:ss((+|-)HH:mm|Z), yyyy-MM-dd'T'HH:mm:ss.[0-9]{1,12}((+|-)HH:mm|Z)]"

I believe there were changes at with DateTime at json-schema-validator

looks like some default date format got changed

java-json-tools/json-schema-validator@728b3da introduce new default behavior

Best not do that in minor version release

fair point

I thought the addition of fractions was optional. I'll add a test and fix the behavior.

I believe it's the lack of colon in your timezone offset.

RFC3339 specifies that offsets should have colons in them:

time-numoffset  = ("+" / "-") time-hour ":" time-minute
time-offset     = "Z" / time-numoffset

https://tools.ietf.org/html/rfc3339#section-5.6

My temptation is to inject a setting to allow you to use the old date time formatter for now, so you can migrate over at your leisure.

@dantran Mind taking a look at:
java-json-tools/json-schema-validator#262